This encapsulates substantial logic to encapsulate interpretation of the
Crucible Common Data Model OpenSearch schema for the use of CPT dashboard API
components. By itself, it does nothing.

This uses `black`, `isort` and `flake8` to check code quality, although
failure is ignored until we've cleaned it up (which has begin in
PR cloud-bulldozer#139 against the `revamp` branch).

Minimal unit testing is introduced, generating a code coverage report.
The text summary is added to the Action summary page, and the more
detailed HTML report is stored as an artifact for download.

NOTE: The GitHub Action environment is unhappy with `uvicorn` 0.15;
upgrading to the latest 0.32.x seems to work and hasn't obviously
broken anything else.

`crucible_svc.py` test coverage is now at 97%. While the remaining 3% is
worth some effort later, the law of diminishing returns will require A
significant additional effort; and since subsequent ILAB PRs will change
some of the service code anyway it's good enough for now.

Provide the `api/v1/ilab` API endpoint to allow a client to query
collected data on a Crucible CDM OpenSearch instance through the
`crucible_svc` service layer. It is backed by the Crucible layer added
in cloud-bulldozer#122, so only the final commit represents changes in this PR.

This covers 100% of the ilab.py API module using `FastAPI`'s `TestClient`.

This proved ... interesting ... as the FastAPI and Starlette versions we use
are incompatible with the underlying httpx version ... TestClient init fails
in a way that can't be worked around. (Starlette passes an unknown keyword
parameter.)

After some experimentation, I ended up "unlocking" all the API-related
packages in `project.toml` to `"*"` and letting `poetry update` resolve them,
then "re-locked" them to those versions. The resulting combination of modules
works for unit testing, and appears to work in a real `./local-compose.sh`
deployment as well.

This adds a mechanism to "can" and restore a small prototype ILAB (Crucible
CDM) Opensearch database in a pod along with the dashboard back end, front
end, and functional tests. The functional tests run entirely within the pod,
with no exposed ports and with unique container and pod names, allowing for
the possibility of simultaneous runs (e.g., a CI) on the same system.

This also has utilities for diagnosing a CDM (v7) datastore and cloning a
limited subset, along with creating an Opensearch snapshot from that data
to bootstrap the functional test pod.

Only a few functional test cases are implemented here, as demonstration. More
will be added separately.

This relies on the ilab API in cloud-bulldozer#123, which in turn builds on the crucible
service in cloud-bulldozer#122.

The `fetchILabJobs` action wasn't updating the date picker values from the API
response unless a non-empty list of jobs is returned. This means that on the
initial load, if the default API date range (1 month) doesn't find any jobs,
the displayed list is empty and the date range isn't updated to tell the user
what we've done.

I've seen no ill effects in local testing from simply removing the length
check, and now the date picker is updated correctly.